-
Notifications
You must be signed in to change notification settings - Fork 0
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Update dependency Pulumi.Kubernetes to v4 #45
Open
renovate
wants to merge
1
commit into
main
Choose a base branch
from
renovate/pulumi.kubernetes-4.x
base: main
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
renovate
bot
force-pushed
the
renovate/pulumi.kubernetes-4.x
branch
3 times, most recently
from
July 21, 2023 18:08
3e51f58
to
4841a81
Compare
renovate
bot
force-pushed
the
renovate/pulumi.kubernetes-4.x
branch
from
August 16, 2023 05:07
4841a81
to
9af1a7c
Compare
renovate
bot
force-pushed
the
renovate/pulumi.kubernetes-4.x
branch
from
August 24, 2023 02:37
9af1a7c
to
d03cb6a
Compare
renovate
bot
force-pushed
the
renovate/pulumi.kubernetes-4.x
branch
from
September 14, 2023 20:10
d03cb6a
to
860bd78
Compare
renovate
bot
force-pushed
the
renovate/pulumi.kubernetes-4.x
branch
from
September 25, 2023 20:04
860bd78
to
26b279b
Compare
renovate
bot
force-pushed
the
renovate/pulumi.kubernetes-4.x
branch
from
October 12, 2023 21:55
26b279b
to
83bbcaf
Compare
renovate
bot
force-pushed
the
renovate/pulumi.kubernetes-4.x
branch
3 times, most recently
from
October 26, 2023 19:37
12bd6f0
to
92e8f14
Compare
renovate
bot
force-pushed
the
renovate/pulumi.kubernetes-4.x
branch
from
November 1, 2023 01:39
92e8f14
to
7f4db9c
Compare
renovate
bot
force-pushed
the
renovate/pulumi.kubernetes-4.x
branch
from
November 9, 2023 00:20
7f4db9c
to
3bad17c
Compare
renovate
bot
force-pushed
the
renovate/pulumi.kubernetes-4.x
branch
from
November 29, 2023 03:51
3bad17c
to
275c732
Compare
renovate
bot
force-pushed
the
renovate/pulumi.kubernetes-4.x
branch
2 times, most recently
from
December 15, 2023 03:13
72e508e
to
54c2692
Compare
renovate
bot
force-pushed
the
renovate/pulumi.kubernetes-4.x
branch
2 times, most recently
from
January 19, 2024 22:36
10f1082
to
73fcfe0
Compare
renovate
bot
force-pushed
the
renovate/pulumi.kubernetes-4.x
branch
2 times, most recently
from
February 27, 2024 01:31
bca7301
to
dec6e93
Compare
renovate
bot
force-pushed
the
renovate/pulumi.kubernetes-4.x
branch
from
March 5, 2024 07:42
dec6e93
to
42d3e45
Compare
renovate
bot
force-pushed
the
renovate/pulumi.kubernetes-4.x
branch
from
March 14, 2024 01:29
42d3e45
to
57bd3e0
Compare
renovate
bot
force-pushed
the
renovate/pulumi.kubernetes-4.x
branch
2 times, most recently
from
April 18, 2024 10:01
3ad0234
to
d72bb99
Compare
renovate
bot
force-pushed
the
renovate/pulumi.kubernetes-4.x
branch
from
May 22, 2024 03:53
d72bb99
to
8ab48b1
Compare
renovate
bot
force-pushed
the
renovate/pulumi.kubernetes-4.x
branch
from
June 5, 2024 01:34
8ab48b1
to
d2bb667
Compare
renovate
bot
force-pushed
the
renovate/pulumi.kubernetes-4.x
branch
from
June 28, 2024 22:33
d2bb667
to
e530b7a
Compare
renovate
bot
force-pushed
the
renovate/pulumi.kubernetes-4.x
branch
from
July 10, 2024 20:04
e530b7a
to
2a185c3
Compare
renovate
bot
force-pushed
the
renovate/pulumi.kubernetes-4.x
branch
2 times, most recently
from
August 13, 2024 22:23
2ff70e4
to
95365df
Compare
renovate
bot
force-pushed
the
renovate/pulumi.kubernetes-4.x
branch
from
August 16, 2024 22:10
95365df
to
8e366c6
Compare
renovate
bot
force-pushed
the
renovate/pulumi.kubernetes-4.x
branch
2 times, most recently
from
September 14, 2024 00:38
9f5c692
to
7883146
Compare
renovate
bot
force-pushed
the
renovate/pulumi.kubernetes-4.x
branch
from
October 16, 2024 22:22
7883146
to
d70aa02
Compare
renovate
bot
force-pushed
the
renovate/pulumi.kubernetes-4.x
branch
from
October 31, 2024 22:59
d70aa02
to
fded3c7
Compare
renovate
bot
force-pushed
the
renovate/pulumi.kubernetes-4.x
branch
from
December 6, 2024 00:13
fded3c7
to
cb65340
Compare
renovate
bot
force-pushed
the
renovate/pulumi.kubernetes-4.x
branch
from
December 12, 2024 06:32
cb65340
to
531ecb6
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR contains the following updates:
3.23.1
->4.19.0
Release Notes
pulumi/pulumi-kubernetes (Pulumi.Kubernetes)
v4.19.0
Changed
v4.18.4
Changed
punycode
deprecation warnings by using nativefetch
instead ofnode-fetch
.https://github.com/pulumi/pulumi-kubernetes/issues/33013301)
Fixed
pulumi.com/waitFor
and other await annotations now correctly take precedence over default await logic.https://github.com/pulumi/pulumi-kubernetes/issues/33293329)
JSONPath expressions used with the
pulumi.com/waitFor
annotation will no longer hang indefinitely if they match non-primitive fields.https://github.com/pulumi/pulumi-kubernetes/issues/33453345)
[java] CRDs that contain any
x-kubernetes-*
fields can now be succesfully created and managed by Pulumi.https://github.com/pulumi/pulumi-kubernetes/issues/33253325)
v4.18.3
Fixed
Objects created on clusters older than 1.18 will no longer see a
before-first-apply
conflict when Pulumi performs a server-side apply forthe first timhttps://github.com/pulumi/pulumi-kubernetes/pull/32753275)
The provider's user agent is now set correctly when communicating with
the Kubernetes API servehttps://github.com/pulumi/pulumi-kubernetes/issues/3267ues/3267)
v4.18.2
Fixed
potential "pulumi.runtime.invokeOutput is not a function" errorhttps://github.com/pulumi/pulumi/issues/17518es/17518)
v4.18.1
Added
Changed
v4.18.0
Added
The new
enableSecretMutable
provider configuration option treats changes toSecrets
as updates instead of replacements (similar to theenableConfigMapMutable
option).The default replacement behavior can be preserved for a particular
Secret
by setting its
immutable
field totrue
.https://github.com/pulumi/pulumi-kubernetes/issues/22912291)
Note: These options (
enableSecretMutable
andenableConfigMapMutable
)may become the default behavior in a future v5 release of the provider.
Programs that depend on the replacement of
Secrets
andConfigMaps
(e.g.to trigger updates for downstream dependencies like
Deployments
) arerecommended to explicitly specify
immutable: true
.A warning is now emitted if an object has finalizers which might be blocking
deletiohttps://github.com/pulumi/pulumi-kubernetes/issues/14181418)
EXPERIMENTAL: Generic await logic is now available as an opt-in feature.
Running a program with
PULUMI_K8S_AWAIT_ALL=true
will now cause Pulumi toawait readiness for all resources, including custom resources.
Generic readiness is determined according to some well-known conventions (like
the "Ready" condition) as determined by cli-utils.
Pulumi's current behavior, without this feature enabled, is to assume some
resources are immediately available, which can cause downstream resources to
fail.
Existing readiness logic is unaffected by this setting.
https://github.com/pulumi/pulumi-kubernetes/issues/29962996)
EXPERIMENTAL: The
pulumi.com/waitFor
annotation was introduced to allowfor custom readiness checks. This override Pulumi's own await logic for the
resource (however the
pulumi.com/skipAwait
annotation still takesprecedence).
The value of this annotation can take 3 forms:
A string prefixed with
jsonpath=
followed by aJSONPath
expression and an optional value.
The JSONPath expression accepts the same syntax as
kubectl get -o jsonpath={...}
.If a value is provided, the resource is considered ready when the
JSONPath expression evaluates to the same value. For example this
resource expects its "phase" field to have a value of "Running":
If a value is not provided, the resource will be considered ready when
any value exists at the given path, similar to
kubectl wait --for jsonpath=...
. This resource will wait until it has a webhook configuredwith a CA bundle:
A string prefixed with
condition=
followed by the type of thecondition and an optional status. This matches the behavior of
kubectl wait --for=condition=...
and will wait until the resource has amatching condition. The expected status defaults to "True" if not
specified.
A string containing a JSON array of multiple
jsonpath=
andcondition=
expressions.Pulumi will now emit logs for any Kubernetes "Warning" Events associated with
resources being created, updated or deletehttps://github.com/pulumi/pulumi-kubernetes/pull/3135ull/3135/files)
Fixed
The
immutable
field is now respected forConfigMaps
when the provider is configured withenableConfigMapMutable
.https://github.com/pulumi/pulumi-kubernetes/issues/31813181)
Fixed a panic that could occur during deletion. (https://github.com/pulumi/pulumi-kubernetes/issues/3157)
v4.17.1
Fixed
ServiceAccounts
. (https://github.com/pulumi/pulumi-kubernetes/issues/3166)clusterIdentifier
provider configuration. (https://github.com/pulumi/pulumi-kubernetes/issues/3168)v4.17.0
Changed
Fixed
Services
with selectors targeting 0Pods
will no longer hang indefinitely.https://github.com/pulumi/pulumi-kubernetes/issues/605/605)
Services
without selectors will no longer hang indefinitely.https://github.com/pulumi/pulumi-kubernetes/issues/799/799)
v4.16.0
Added
clusterIdentifier
configuration can now be used to manually control thereplacement behavior of a provider resourchttps://github.com/pulumi/pulumi-kubernetes/pull/3068ull/3068)
Pod errors now include the pod's last termination state, as well as the pod's
termination message if availablhttps://github.com/pulumi/pulumi-kubernetes/pull/3091ull/3091)
The pod's termination message can be helpful in
CrashLoopBackOff
situations butwill only be reported if it was correctly configured.
By default, the pod's termination message is read from
/dev/termination-log
. This location can be configured withterminationMessagePath
.Use
terminationMessagePolicy: FallbackToLogsOnError
to use the pod's logsas its termination message.
Documentation is now generated for all languages supported by overlay types.
https://github.com/pulumi/pulumi-kubernetes/pull/31073107)
Fixed
CustomResource
overlays. (https://github.com/pulumi/pulumi-kubernetes/pull/3120)affected resourchttps://github.com/pulumi/pulumi-kubernetes/pull/31283128)
PersistentVolumeClaims
with a bind mode ofWaitForFirstConsumer
will nolonger hang indefinitelhttps://github.com/pulumi/pulumi-kubernetes/pull/31303130)
v4.15.0
Changed
CustomResource
should have plainapiVersion
andkind
properties (https://github.com/pulumi/pulumi-kubernetes/pull/3079)https://github.com/pulumi/pulumi-kubernetes/pull/31443144)
Fixed
v4.14.0
Added
TypedDict
input types for the Python SDK (https://github.com/pulumi/pulumi-kubernetes/pull/3070)Changed
Release
resource no longer ignores empty lists when merging values. (https://github.com/pulumi/pulumi-kubernetes/pull/2995)Fixed
Chart
v4 now handles an array of assets. (https://github.com/pulumi/pulumi-kubernetes/pull/3061)v4.13.1
Added
Changed
Fixed
replaceUnready
annotations and an unreachable cluster connection. (https://github.com/pulumi/pulumi-kubernetes/pull/3024)v4.12.0
Added
Changed
valueYamlFiles
now more closely matches Helm's behavior. (https://github.com/pulumi/pulumi-kubernetes/pull/2963)Fixed
null
. (https://github.com/pulumi/pulumi-kubernetes/issues/1970)v4.11.0
v4.10.0
New Features
A new MLC-based implementation of
ConfigGroup
and ofConfigFile
is now available in the "yaml/v2" package. These resources areusable in all Pulumi languages, including Pulumi YAML and in the Java Pulumi SDK.
Note that transformations aren't supported in this release (see https://github.com/pulumi/pulumi/issues/12996).
v4.9.1
helm
,kustomize
, andyaml
components (https://github.com/pulumi/pulumi-kubernetes/pull/2863)v4.9.0
v4.8.1
v4.8.0
v4.7.1
v4.7.0
Breaking Changes
In previous versions of the pulumi-kubernetes .NET SDK, the
ConfigFile
andConfigGroup
component resources inadvertently assigned the wrong parent to the child resource(s).This would happen when the component resource itself had a parent; the child would be assigned that same parent. This also had the effect of disregarding the component resource's provider in favor of the parent's provider.
For example, here's a before/after look at the component hierarchy:
Before:
After:
This release addresses this issue and attempts to heal existing stacks using aliases. This is effective at avoiding a replacement except in the case where the child was created with the wrong provider. In this case, Pulumi will suggest a replacement of the child resource(s), such that they use the correct provider.
v4.6.1
v4.6.0
PULUMI_KUBERNETES_MANAGED_BY_LABEL
env var with SSA created objects (https://github.com/pulumi/pulumi-kubernetes/pull/2711)Resources Renamed:
#/types/kubernetes:core/v1:ResourceRequirements
#/types/kubernetes:core/v1:VolumeResourceRequirements
#/types/kubernetes:core/v1:ResourceRequirementsPatch
#/types/kubernetes:core/v1:VolumeResourceRequirementsPatch
New Resources:
flowcontrol.apiserver.k8s.io/v1.FlowSchema
flowcontrol.apiserver.k8s.io/v1.FlowSchemaList
flowcontrol.apiserver.k8s.io/v1.FlowSchemaPatch
flowcontrol.apiserver.k8s.io/v1.PriorityLevelConfiguration
flowcontrol.apiserver.k8s.io/v1.PriorityLevelConfigurationList
flowcontrol.apiserver.k8s.io/v1.PriorityLevelConfigurationPatch
networking.k8s.io/v1alpha1.ServiceCIDR
networking.k8s.io/v1alpha1.ServiceCIDRList
networking.k8s.io/v1alpha1.ServiceCIDRPatch
storage.k8s.io/v1alpha1.VolumeAttributesClass
storage.k8s.io/v1alpha1.VolumeAttributesClassList
storage.k8s.io/v1alpha1.VolumeAttributesClassPatch
v4.5.6
v4.5.5
v4.5.4
v4.5.3
v4.5.2
v4.5.1
v4.5.0
v4.4.0
v4.3.0
v4.2.0
source-based and wheel distributions are now published. For most users the installs will now favor
the wheel distribution, but users invoking pip with
--no-binary :all:
will continue havinginstalls based on the source distribution.
v4.1.1
(https://github.com/pulumi/pulumi-kubernetes/issues/25402540)
v4.1.0
v4.0.3
v4.0.2
v4.0.1
v4.0.0
Breaking changes:
Other changes:
v3.30.2
v3.30.1
v3.30.0
v3.29.1
v3.29.0
v3.28.1
v3.28.0
SelfSubjectReview, SelfSubjectAccessReview, SelfSubjectRulesReview, and SubjectAccessRevihttps://github.com/pulumi/pulumi-kubernetes/pull/24132413)
v3.27.1
v3.27.0
v3.26.0
v3.25.0
New resources:
Resources moved from v1alpha1 to v1alpha2
Resources moved from v1beta1 to v1
Resources renamed
New Features
v3.24.3
v3.24.2
v3.24.1
invoke_yaml_decode
into ConfigGroup for python (https://github.com/pulumi/pulumi-kubernetes/pull/2317)v3.24.0
outputs
afterSecret.get
(https://github.com/pulumi/pulumi-kubernetes/pull/2300)Configuration
📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Whenever PR is behind base branch, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about this update again.
This PR was generated by Mend Renovate. View the repository job log.